Compensation based on entity groups

ABSTRACT

Various implementations for providing compensation based at least in part on a number of entity groups are described. A relationship network associated with an entity includes a plurality of network entities. The relationship network is determined, and a number of entity groups within the relationship network are counted. The entity groups have a predetermined number of network entities. An entity is caused to be provided with compensation that is based at least in part on the number of entity groups in the relationship network.

RELATED APPLICATIONS

This application is a continuation of co-pending, commonly owned U.S.patent application Ser. No. 13/452,479, now U.S. Pat. No. 8,788,384,filed Apr. 20, 2012, issued on Jul. 22, 2014, and entitled “CompensationBased On Entity Groups,” which is related to U.S. application Ser. No.13/421,616 filed on Mar. 15, 2012, and entitled “Mobile ServiceDistribution and Provisioning Architecture,” the entire contents ofwhich are hereby incorporated herein by reference in their entirety forall purposes.

BACKGROUND

Conventional direct sales models pay commissions based on a percentageof the purchases made by individuals within a member's network. The moreproducts sold within a member's network, the higher the commissions paidto the member. A member's network grows when the member adds directrecruits to the network. Also, the member's network grows when othermembers within his or her network recruit new members.

A conventional direct sales network therefore has multiple levels.Recruits of recruits are two levels away from the member. Individualsrecruited by members two levels away are three levels away from themember, and so forth. Because purchases made anywhere within the networkdrive additional commissions for the member, members have an incentiveto help their recruits sell product and to help their recruits recruitnew individuals into the network. But in order to maintain thesustainability of a conventional direct sales model, the member is paida lower percentage of the purchases made at levels far away from themember.

BRIEF SUMMARY

This Summary is provided in order to introduce simplified concepts ofthe present disclosure, which are further described below in theDetailed Description. This summary is not intended to identify essentialfeatures of the claimed subject matter, nor is it intended for use indetermining the scope of the claimed subject matter.

Revenue sharing models compensate members (also referred to herein as“entities”) based at least in part on the size of their relationshipnetworks, and in particular based at least in part on the number ofentity groups within their relationship networks. An entity group is apredetermined number of entities with common connections to a singleentity within the relationship network. Revenue sharing models includemultiple phases. In a first phase, entities receive compensation forrecruiting personal connections into the relationship network. In asecond phase, the entities receive compensation based at least in parton the number of entity groups their personal connection entitiesrecruit. In a third phase, the entities receive compensation based atleast in part on the total number of entity groups within theirrelationship networks, no matter how many levels down in therelationship network those entity groups are.

BRIEF DESCRIPTION OF THE DRAWINGS

The Detailed Description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 is a schematic diagram of an example system for acquisition ofnew members using mobile device tools.

FIG. 2 is a schematic diagram of an example system for acquisition ofnew members using social media tools.

FIG. 3 illustrates an example environment for providing commissionsbased at least in part on purchases made at participating retailers.

FIG. 4 illustrates an example relationship network during a first phaseof an example revenue sharing model.

FIG. 5 illustrates an example relationship network during a second phaseof an example revenue sharing model.

FIG. 6 illustrates an example relationship network during a third phaseof an example revenue sharing model.

FIG. 7 is a block diagram of an example computing system usable toprovide a transaction service.

FIG. 8 is a flow diagram showing an example process for providingcompensation based at least in part on a number of entities in arelationship network.

DETAILED DESCRIPTION Overview

Embodiments of the present disclosure include revenue sharing modelsthat are sustainable and that provide incentives for members to assistindividuals in their networks, no matter how many levels away in therelationship network those individuals are. As noted above, inconventional direct sales models, members are paid lower percentages ofthe revenue generated at far-away levels within their networks. Thus,members in conventional direct sales models have little or no incentiveto assist individuals at far-away levels to generate revenue throughsales or to recruit new members.

Embodiments of the present application include revenue sharing modelsthat pay members based at least in part on the size of their networks.The larger a member's network is, the more commissions that the memberearns. In embodiments, the member is paid one-time or monthly-recurringbonuses based at least in part on the number of members (also referredto herein as “entities”) within their networks. In embodiments, membersare paid based at least in part on the number of entity groups withintheir networks. An entity group may be defined as a predefined number ofentities (i.e., members) that all share a common connection to a singleentity within a relationship network. For example, an entity group maybe defined as a trio—three members—who have all been recruited by thesame common entity. Other groupings may be used without departing fromembodiments. For example, groups of two, four, five, six, or moreentities may comprise an entity group.

Embodiments provide members with compensation based at least in part oncompensation tiers and compensation bands. A member may receive bonusesat a first level when his or her relationship network reaches a firsttier based at least in part on his or her relationship network having afirst number of entities or entity groups. A member may receive bonusesat a second, higher, level if his or her relationship network reaches asecond tier based at least in part on his or her relationship networkhaving a second, higher, number of entities or entity groups. Likewise,groups of tiers, such as two, three, four, or more tiers, are groupedinto compensation bands. Members may be provided one-time or monthlyrecurring compensation based at least in part on their relationshipnetworks reaching a tier within a compensation tier or band that themember had not previously reached. This provides members with anincentive to continue growing the size of their networks.

Members are also compensated based on achieving every n^(th) entitygroup, for example every second, third, fourth, fifth, sixth entitygroup, or other number of entity groups, within a personal networkportion of a relationship network. A personal network may be the definedas those entities with direct connections to the member. In otherembodiments, the personal network may include entities at levels one andtwo (those with direct connections to the member plus those with directconnections to those with direct connections to the member). Moregenerally, a personal network includes entities at levels 1:m below themember, with m being an integer.

Compensation according to embodiments may be provided as one or more ofcash, credit, store credit (such as for participating vendors), giftcards, travel rewards, vehicle allowances, debt forgiveness, airlinemiles or other loyalty reward program credits, and so forth. Inembodiments, compensation may be provided by depositing funds into anaccount associated with a debit card as is described in more detailbelow. Compensation may be provided on a one-time basis or on arecurring basis (such as hourly, daily, weekly, monthly, quarterly,annually, and so forth). Embodiments are not limited to providingcompensation in these ways, and other compensation types are availablewithout departing from the scope of embodiments.

Embodiments described herein include revenue sharing models for servicesthat yield periodically recurring charges (such as daily, weekly,monthly, or yearly recurring charges). Such services include, but arenot limited to, mobile phone services, internet services, cableservices, energy services, and so forth. In these embodiments, membersare provided with compensation—either one-time compensation orperiodically recurring compensation—based at least in part on the numberof entities, or entity groups, within the members' relationshipnetworks.

Other embodiments described herein share revenue that is generated fromproduct purchases, such as purchases made by members at participatingretailers. In various embodiments, compensation is provided to membersby depositing money into an account linked to a debit card. Thepurchases made on those debit cards are then tied back to the members'accounts, and compensation is determined from this data. In theseembodiments, a certain percentage of the revenue from these purchases isset aside for sharing with members. In embodiments, a member is paid apercentage of the set aside revenue based at least in part on the numberof entities, or the number of entity groups, within his or herrelationship network (such as for example based at least in part on themember's compensation tier or band).

Because a member is paid based at least in part on the number ofentities, or the number of entity groups, at any level within themember's relationship network, the member has an incentive to assistmembers at all levels of his or her relationship network obtain newmembers. Because there are gaps between compensation tiers, the modelcan be made sustainable. For example, a first tier may be based at leastin part on having ten entities in a member's relationship network, whilea second tier may be based at least in part on having 20 entities in themember's relationship network. In this example, the gap of ten entitiesbetween the first and second tiers enables the revenue sharing model tobe sustainable—e.g., it does not pay out an exponential amount of moneyto the members—while maintaining an incentive for the members to assistentities within their relationship networks no matter how many levelsaway those entities are.

The processes, systems, and devices described herein may be implementedin a number of ways. Example implementations are provided below withreference to the following figures.

Example Environments for New Member Acquisition

Next, an example direct sales model related to mobile service will bedescribed. Embodiments are not limited to this direct sales model.Later, example revenue sharing models based at least in part on networksize and compensation tiers will be described.

FIG. 1 is a schematic diagram of an example system 100 for acquisitionof new members using mobile device tools. Aspects of the system 100 maybe implemented on various suitable computing device types. Suitablecomputing device or devices may include, or be part of, one or morepersonal computers, servers, server farms, datacenters, special purposecomputers, tablet computers, game consoles, smartphones, media players,combinations of these, or any other computing device(s).

Member 102 is a mobile service subscriber and he or she accesses amobile service using a mobile device 104. During interaction with aprospective member 106, the member 102 is able to use the mobile device104 to access transaction service 108 via a network 110. The member 102interacts with a user interface on mobile device 104 to launch one ormore transaction screens, such as transaction screen 112, which enablethe prospective member 106 to sign up for new service and to become amember.

The one or more transaction screens provide input fields for the member102 and/or the prospective member 106 to input the prospective member'sinformation to sign up for the service. Through the one or moretransaction screens, the prospective member 106 and/or the member 102selects a desired handset make and model, enters in existing mobileservice information, enters in their address and credit cardinformation, and so forth. The prospective member 106 also selects phonedelivery methods, and provides other information to customize their newservice and to facilitate signing up for new service. The mobile device104 may include a camera or other scanner for imaging or otherwisescanning the prospective member's credit card. In embodiments, mobiledevice 104 may be equipped with Bluetooth or other short-range wirelesscapability in order to serve up the transaction screens directly to theprospective member's 106 existing mobile device so that the prospectivemember 106 can enter the information directly into their own existingdevice.

In one embodiment, the mobile device 104 accesses a web service 114 viaan installed browser and a soft link on a user interface screen of themobile device 104. In these embodiments, the one or more transactionsscreens are served by the web service 114, and the prospective member'sinformation is provided to the transaction service 108 via the webservice 114 and the network 110. One or more transaction screens may becached or stored locally on the mobile device 104 to enable the browserto access them directly rather than via the web service 114.

In another embodiment, the mobile device 104 includes an installedapplication that accesses the transaction platform 116 directly, orthrough the web service 114. The installed application may present theone or more transaction screens and transmit the prospective member'sinformation to the transaction service 108 via the network 110.Alternatively, the installed application may download the transactionsscreens, or portions of the transaction screens, from the web service114 or other portion of the transaction service 108.

A transaction platform 116 creates a new member account for theprospective member 106 in a secure member database. The transactionplatform 116 associates the new member account or service with themember's 102 existing account or service, thereby adding to arelationship network for the member 102. The new member account orservice may also be associated with other members' accounts or servicesin whose relationship networks member 102 is a member. These otheraccounts or services may include an account or service of a member whosigned up the member 102 and accounts or services of other members abovethe member who signed up the member 102. Based at least in part on theseassociations, the transaction platform 116 is enabled to provide member102, as well as other associated members, with benefits—such ascommissions—for signing up the prospective member 106.

The transaction platform 116 interacts with one or more third partyproviders 118 via various corresponding third party adaptors 120. Thethird party providers may include, among other things, a commissioningprovider, a fulfillment provider, a bank provider, a social networkingprovider, and so forth. The third party providers 118 carry out variousfunctions on behalf of the transaction service 108.

In one example, a fulfillment provider may be instructed by thetransaction platform 116 to ship a new mobile device 122 to prospectivemember 106. In this illustration, the new mobile device 122 arrives in abox 124, although in other implementations, the new mobile device may bedelivered to the prospective member 106 in other ways. The prospectivemember 106 activates the new mobile device 122 and begins using themobile service. The prospective member 106 may opt-in during theactivation process or at some other time to use his or her existingsocial networking services to seek out new members. New mobile device122 comes pre-configured with the same or similar member acquisitiontools as are on the mobile device 104. Thus, the prospective member 106is also enabled to seek out and sign up additional members.

The prospective member may also have the option to receive a SubscriberIdentity Module (SIM) card in lieu of a new mobile device, such as wherethe prospective member's existing mobile device is compatible with themobile service. Upon receipt of the SIM card, the prospective member canswap out their old SIM card for the new SIM card and activate their newservice using their existing mobile phone.

The network 110 may include one or more wired and/or wireless networkssuch as the public Internet, local area networks, wide area networks,mobile carrier networks, personal area networks (PAN), and so forth. Themobile device 104 may access the network 110 using various technologiessuch as through Bluetooth® or other PAN technologies, Wi-Fi®technologies based on the IEEE 802.11 family of standards, Global Systemof Mobile Communication (GSM) standards-based technologies, codedivision multiple access (CDMA) mobile phone standards, and so forth.Embodiments of the present disclosure are not limited to any type ortypes of networking technologies or protocols.

In various embodiments, the member 102 may utilize something other thana mobile phone to access the network 110 and sign the prospective member106 up to a new service. Thus, mobile device 104 may be a mobile phone(such as a smartphone), a tablet computer, a laptop computer, a netbookcomputer, a personal computer, or other device that has access to thenetwork 110. Embodiments are not limited to particular type or types ofdevices for accessing the transaction service 108.

The transaction service 108 also includes motivation platform 126. Themotivation platform 126 provides real-time, highly relevant alerts,messages, and reports that include data indicating activities that themember 102 may engage in to achieve additional levels of compensation orto reach other goals. Such messages are meant to motivate the member 102to perform these activities, thereby driving additional member sign-upsand other revenue-generating activities. For example, the motivationplatform 126 may determine, based at least in part on commissioninginformation provided by the transaction platform 116, that the member102 may achieve a reward, commission, or other compensation by signingup a certain number of additional new members to his relationshipnetwork, by attending webinars, or by engaging in other activities. Inanother example, the motivation platform 126 may determine that the newmember 102 may achieve a new compensation tier, thereby enabling themember 102 to receive additional compensation, by signing up a certainnumber of new members to his or her network.

The motivation platform 126 creates a report, social network feed,email, alert, instant message, or other communication that includes thedetermined information and transmits it to the member 102. This mayinclude sending social networking messages, via the third partyadaptors, to reach a social networking provider. Alternatively or inaddition, the motivation platform 126 may host or be associated with asocial networking service that is accessible via the web service 114.The social networking messages may include message feeds, messages,reporting screens, and so forth. By providing the user with real-time,highly relevant data, the motivation platform is able to inform themember 102 as to those activities that he or she may perform to reachtheir commissioning goals. Various ones of the messages, reports, andalerts may be accessible to the member 102 via a member page, such asvia a social networking page that is hosted by the transaction service.

The environment of FIG. 1 depicts a real-time interaction between themember 102 and the prospective member 106. Next, social media tools foracquisition of new members will be described.

FIG. 2 is a schematic diagram of an example system 200 for acquisitionof new members using social media tools. Referring to FIG. 2, aprospective member 202 accesses social media provider 204 using thepersonal computer 206. In embodiments, the prospective member 202 mayutilize a netbook computer, a mobile phone, a tablet computer, or otherdevice suitable for accessing the social media provider 204.

The personal computer 206 downloads social media page 208, whichincludes social media content. In one example, the social media page 208is a social media page for an existing mobile service member, such asthe member 102. The content on the social media page 208 includes a linkto the web service 114. Clicking on the link within social media page208 enables the prospective member 202 to browse to the web service 114and to sign up for service through the transaction platform 116. Uponentering in their personal information and signing up for new mobileservice, the prospective member 106 receives the new mobile device 122(or a new SIM card) through a fulfillment provider of the third partyproviders 118 in the same or similar manner as is described withreference to FIG. 1.

The link to the web service 114 includes a resource identifier—such asuniversal resource identifier (URI) or a universal resource locator(URL)—that enables the personal computer 206 to access the web service114. The link also includes embedded information that enables thetransaction platform 116 to associate the existing member service withthe newly created member service for the prospective member 106. Thisembedded information may be included as part of the URI or URL of thelink. The embedded information may include some or all of the existingmember's name, the existing member's phone number, the existing member'saccount number, a member number, or an anonymous identifier.

In this way, social media tools enable an existing member's onlinesocial media network to be leveraged for acquisition of new members. Thetransaction platform 116 utilizes the embedded information within socialmedia links to associate the existing member's account or service to thenew memberships that are generated through the link. The transactionplatform 116 is configured to initiate bonus or commission payments forthe existing member based at least in part on these associations, as isdescribed below.

Example Participating Retailer Environment

FIG. 3 illustrates an example environment 300 for providing commissionsbased at least in part on purchases made at participating retailers. Amember 302 receives compensation for participating in a revenue sharingmodel according to embodiments. In embodiments, the compensation thatthe member receives is deposited into an account, such as may be hostedby bank, which is one of the third party providers 118. The transactionplatform 116 calculates compensation owed to the member 302 and causesit to be deposited into the account, such as for example via the thirdparty adaptors 120. The account is associated with a transaction card304, which may be a debit card, a credit card, member identificationcard, or other card type. The member 302 may utilize the transactioncard 304 to make purchases at retailers that accept the transaction card304. In alternative embodiments, the member 302 may utilize some othermechanism to correlate his or her purchases with the participatingretailers 306 back to his or her member account. For example his or hermobile device (such as the mobile devices 104 and 122) may be used tomake purchases. The transaction card 304 is just one mechanism to makepayment at participating retailers 306. The member 302 may use insteadof, or in addition to, his or her mobile phone 308 to make a paymentswith the participating retailers 306.

Some or all of the retailers that accept the transaction card 304 forpurchases may be participating retailers 306. The participatingretailers 306 provide a portion of the revenue from purchases made bymembers at the participating retailers 306 to the transaction service108. The participating retailers 306 may be traditional “brick andmortar” retailers, or online retailers, or have both traditional andonline retail operations. Purchases made by members with theparticipating retailers 306 may be used to calculate additionalcompensation for the member 302. For example, the transaction platform116 may calculate compensation for the member 302 based at least in parton the portion of the purchases made by the member 302 and/or thepurchases made by other members that are within his or her relationshipnetwork, as is described in more detail below.

Example Relationship Networks

FIGS. 4-6 illustrate example relationship networks. Revenue sharingmodels according to embodiments utilize the size of a member'srelationship network, such as the number of entity groups within therelationship network, to determine the level of compensation provided tomembers. An example revenue sharing model—described with reference toFIGS. 4-6—includes several components meant to address various stages ofdevelopment of a member's relationship network. The first phase of theexample revenue sharing model provides incentives for the member torecruit new entities to the network. The first phase is put in placeduring a ramp-up period, such as for a period of time between 30 and 120days, or other time period. The second phase of the example revenuesharing model provides incentives for a member to assist his personalentity connections—those entities that the member directly recruited—torecruit new members. The second phase of the example revenue sharingmodel may also last for a limited period of time, such as for the first30-120 days of the member's association with the model. The third phaseof the example revenue sharing model provides various incentives overthe long term for the member to continue to grow his or her relationshipnetwork and drive purchases by members of his network at any levelwithin the relationship network.

FIG. 4 illustrates an example relationship network 400 during a firstphase of an example revenue sharing model. An entity 402—such as member102—sits atop the relationship network 400. The entity 402 may start outwith no other entities within its relationship network 400, buteventually recruits personal connection entities 404-412. For example,the prospective member 106 may be one of the personal connectionentities 404-412 within the relationship network 400. The personalconnection entities 404-412 may also recruit additional network entities414-422 into the relationship network 400.

In the first phase of the example revenue sharing model, which may lasta specified period of time such as 30-120 days or other time period, theentity 402 receives a one-time and/or monthly bonus based at least inpart on the number of personal connection entities within therelationship network 400. In one non-limiting example, the entity 402 isprovided with a one-time per-connection bonus, such as a $5 bonus orother bonus or compensation (such as gift cards, vendor credit, etc.),for each one of personal connection entities 404-412 within therelationship network 400. Because there are five personal connectionentities in the example relationship network 400, entity 402 mayreceive, according to this example, a $25 one-time bonus. These bonusesmay be monthly recurring, such as during the 30-120 day ramp-up period,some period of time longer than the ramp-up period, or indefinitely foras long as personal connection entities 404-412 signed up during theramp-up period remain part of the relationship network 400.

During the first phase of the example revenue sharing model, the membermay also receive monthly recurring or one-time compensation based atleast in part on the number of entity groups within its personalconnection entities 404-412. In the example shown in FIG. 4, an entitygroup is characterized as having three entities (a “trio”), and personalconnections 404, 406, and 408 form an entity group 424. Other entitygroups, having different numbers of entities, may be used withoutdeparting from the scope of embodiments. Were entity 402 in the exampleshown in FIG. 4 to recruit one more personal connection entity, thenrelationship network 400 would have two entity groups. Were the entity402 then to recruit a further three, six, or nine additional personalconnection entities, then the relationship network 400 would have three,four, and five entity groups, respectively.

In a non-limiting example, the example revenue sharing model may providemembers with a one-time entity group bonus for recruiting personalconnection entities during a ramp-up period (or other time period)according to the following table:

TABLE 1 Number of entity groups One-time bonus 1 $50 2 $100 3 $200 4$300

Upon recruiting the first entity group within its personal connectionentities, the entity 402 would receive a $50 bonus. Upon recruiting thesecond entity group, the entity 402 would receive an additional $100bonus, and so forth. Were the entity 402 to recruit four entity groups(twelve total personal connection entities), the entity 402 wouldreceive a total bonus of $650 ($50+$100+$200+$300). More or fewer entitygroup bonus levels, and smaller or larger bonuses may be paid at thedifferent levels, without departing from the scope of embodiments. Thefirst phase of the example revenue sharing model thus provides anincentive for the entity 402 to bring in personal connection entitiesduring the ramp-up period.

FIG. 5 illustrates an example relationship network 500 during a secondphase of an example revenue sharing model. The entity 402 sits atop therelationship network 500. In the example shown in FIG. 5, therelationship network 500 includes personal connection entities 404-412.The personal connection entities 404-412 may also recruit additionalnetwork entities into the relationship network 500.

During the second phase of the example revenue sharing model, the entity402 is provided with compensation based at least in part on the numberof personal entity groups 502 within a personal network portion of therelationship network 500. In the example shown in FIG. 5, a personalentity group is characterized as having a predetermined number ofentities, such as three entities (a “trio”), with direct connections toa common one of personal connection entities 404-412. A personal entitygroup may have more or fewer entities without departing from the scopeof embodiments. In one non-limiting example, as illustrated in Table 2,the entity 402 is provided a one-time or recurring bonus of $20 based atleast in part on the number of personal entity groups 502 withinrelationship network 500. In the example shown in FIG. 5, networkentities 410, 412, 504 and 506 are part of a personal network portion ofthe relationship network 500, but are not part of a personal entitygroup. Were the entity 402 to add one more personal connection, oreither of personal connection entities 410 or 412 to add two moreentities to the relationship network 500 directly under them, thenrelationship network 500 would have an additional personal entity group.

TABLE 2 Number of personal entity groups One-time bonus 1 $20 2 $40 3$60 4 $80

As discussed above with respect to FIG. 4, the personal connectionsentities 404-412 receive compensation for bringing in personalconnection entities during at least the first phase of the revenuesharing plan. And the example revenue sharing model also provides anincentive, during at least the second phase, for entity 402 to assistthe personal connection entities 404-412 in bringing in more entities,thereby aligning the interests of the entity 402 and the personalconnection entities 404-412.

FIG. 6 illustrates an example relationship network 600 during a thirdphase of an example revenue sharing model. The entity 402 sits atop therelationship network 600. In the example shown in FIG. 6, therelationship network 600 includes personal connection entities 404-412.In the third phase of the example revenue sharing model, which may lastan indefinite period of time for as long as the entity 402 remains amember, the entity 402 receives compensation for the number of personalentity groups 502 with a personal network and/or the number of networkentity groups 602 within an extended network of the relationship network600. In the example shown in FIG. 6, the personal network is defined asthose entities and entity groups above line 604, thereby including twolevels of entities within the personal connection network. Embodimentsinclude relationship networks that include more or fewer levels withinthe personal connection network. The extended network may be defined asincluding those levels below the line 604. A network entity group 602 ischaracterized as having a predetermined number of entities (such asthree entities, i.e., a “trio”) with connections to a common one of anetwork entity other than the personal connection entities 404-412. A“network” entity is either a personal connection entity or anon-personal connection entity.

The entity 402 receives compensation based at least in part on thenumber of entity groups, including the number of personal entity groups,within the relationship network. An entity group is either a personalentity group or an entity group. In embodiments, the entity is providedwith compensation based at least in part on a combination of the numberof entity groups and the number of the entity groups that are personalentity groups. The following table is a non-limiting example of arevenue sharing model that provides compensation based at least in parton a combination of the number of entity groups and the number of entitygroups that are personal entity groups.

TABLE 3 No. of No. which One-time Monthly network are personal Line %Career Career Product Band Tier entity groups entity groups Rule RulePath bonus Path Bonus Sales % 1 1a 1 1 1 100%  $0 $0 3.3% 1b 3 1 $0 $201c 5 2 $0 $50 2 2a 10 2 3 50% $800 $200 2.1% 2b 25 3 $0 $500 2c 50 4 $0$1000 3 3a 100 6 6 40% $3000 $2000 1.05%  3b 200 7 $0 $3000 3c 300 8 $0$4000 4 4a 400 10 9 40% $5000 $5000 .35% 4b 500 11 $0 $6000 4c 600 12 $0$8000 5 5a 800 14 12 40% $15,000 $10,000 .35% 5b 900 16 $0 $15,000 5c1000 20 $30,000 $20,000

Table 3 is split up into fifteen compensation tiers grouped into fivecompensation bands. Although the five compensation bands are labeled1-5, and the fifteen compensation tiers are labeled 1 a, 1 b, 1 c, andso forth, other labels or names may be used in various embodiments.Also, more or fewer tiers and/or compensation bands may be used invarious embodiments. According to the example shown in Table 3, theentity 402 obtains a total of one entity groups, of which at least oneentity group is a personal entity group (an entity group within thepersonal network portion of relationship network 600), in order to reachcompensation tier 1 a. Thus, as long as the entity 402 has at least onepersonal entity group, the entity 402 achieves compensation tier 1 a. Toreach the 1 b compensation tier, the entity 402 obtains three entitygroups in the relationship network 600, of which at least one is apersonal entity group. To reach tier 3 b, the entity 402 obtains 200entity groups, of which at least seven are personal entity groups, andso forth.

The entity 402 is provided with either one-time compensation or amonthly compensation based at least in part on the achieved compensationtier and/or compensation band. In the example shown in Table 3,achieving compensation tier 1 c results in the entity 402 receiving$50/month in compensation. Achieving compensation tier 2 a, on the otherhand, results in the entity 402 receiving a one-time bonus of $800 and a$200/monthly compensation. The entity 402 receives a one-time bonus of$800 based at least in part on achievement of a compensation tier withina compensation band that the entity 402 had not previously achieved.

The entity 402 may also receive a personal network bonus or compensationbased on the number of entity groups within the personal network. Thisis in addition to the monthly or one-time career path bonus described inTable 3, and may be separate from the compensation tier determination.In embodiments, the entity 402 may receive a one-time or recurringpersonal network bonus for every n^(th) entity group within the personalnetwork. In one example, the entity 402 receives the personal networkbonus for every third entity group (which may be called a “triple trio”or “trip trio” in embodiments where three entities form an entitygroup), and thus would receive increased personal network bonuses forevery 3^(rd), 6^(th), 9^(th), and 12^(th) personal entity group, and soon.

Other personal network bonuses are possible without departing from thescope of embodiments. For example, the entity 402 may be compensatedbased on the number of entities (not the number of entity groups) withinthe personal network. Also, a personal entity group within the personalnetwork may have fewer or more entities than an entity group within theextended network. In one such example, a personal entity group includesthree entities while an entity group within the extended networkincludes five entities.

The entity 402 receives compensation based at least in part on thenumber of entities within the relationship network 600. When determiningthe compensation tier or band that the entity 402 achieves, it does notmatter, in embodiments, how many levels below the entity 402 theentities or entity groups within the extended network are. The entity402 achieves the same compensation tier for entities far down in theextended network as for those closer to the top of the extended network.Thus, the entity 402 has an incentive to assist entities anywhere withintheir relationship networks recruit new entities.

Achieving a compensation tier or band may be subject to variousconstraints. Two example constraints are the line rule and the percentrule, as are described below. Other constraints are possible withoutdeparting from the scope of embodiments.

Line Rule

The line rule constraint, as indicated by the “line rule” column inTable 3, indicates the number of personal connection entities that theentity 402 achieves in order to achieve a particular compensation band.In the example shown in Table 3, to achieve compensation band 3, theentity 402 obtains at least six personal connection entities (notpersonal entity groups). Thus, where the line rule constraint applies,the compensation tier or band achieved by the entity 402 is determinedboth by the number of entity groups within the personal network (thefourth column of Table 3) as well as the number of personal connectionentities.

Percent Rule

The Percent rule constraint, as indicated by the “% rule” column inTable 3, indicates a maximum percentage of the network entities orentity groups that are allowed to come under a single personalconnection entity in order to achieve a compensation tier. In theexample shown in Table 3, to achieve compensation band 3, the entity 402obtains at least 100 entity groups with no more than 40% of themconnected to the entity 402 through a single personal connection entity.For example, if the entity 402 had 100 entity groups in the network 600,but more than 40 of those entity groups were under personal connectionentity 404, then the entity 402 would not achieve compensation band 3,and would remain at compensation tier 2 c within compensation band 2.

Purchase Revenue Bonuses

The “product sales” column in Table 3 indicates a percentage of revenuesthat the entity 402 receives for certain purchases made by entitieswithin the relationship network 600. As noted elsewhere within thisDetailed Description, entities may be provided with compensation bydepositing funds into a bank account connected to a transaction card.The entities use the transaction card to make purchases. In otherembodiments, alternative payment mechanisms are used to access thecompensation funds. For example, the entity 402 may utilize paymenttechnology on their mobile device, such as the mobile device 104, tomake payments.

When purchases are made by the entities at participating retailers, theparticipating retailers provide a portion of the purchase back to therevenue sharing model. A percentage of the revenue provided to therevenue sharing model is set aside for compensating the entities (suchas the entities in the relationship network 600, as well as otherentities in other relationship networks). Depending on the compensationtier achieved by the entity 402, the entity receives a first purchasebonus that is based at least in part on a percentage of a first portionof the set-aside revenue that is attributable to the purchases made bythe entities within relationship network 600.

In embodiments, a second purchase bonus not shown in Table 3 is paid toentities based at least in part on their own personal purchases. Forexample, a second portion of the set-aside revenue may be paid to theentities based at least in part on a ratio of the entities'personally-generated revenue to overall revenue generated from allpurchases by all entities. Thus, in one example, if purchases made bythe entity 402 account for 5% of all revenue generated from purchases atparticipating retailers, then the entity 402 would receive 5% of thesecond portion of the set aside revenue.

Top Performer Bonus

Revenue sharing models according to embodiments also provide a topperformer bonus, paid to those entities participating in the revenuesharing model designated as a “top performer.” The top performer bonusmay be paid out of a pool of funds that represents a percentage of grossrevenues, or some other pool. The top performer bonus is paid to the topperformers for certain activities, such as signing up personalconnection entities, adding entity groups to their networks, advancingto a new compensation tier or compensation band, and so forth. The topperformer bonus may be provided on a daily, weekly, monthly, quarterly,or annual basis, or on some other time basis.

New Member Bonus

Revenue sharing models according to embodiments also provide a newmember bonus, paid to entities that have joined within a certain periodof time, such as for example between 30-120 days or other time period.The new member bonus may be paid out of a pool of funds that representsa percentage of gross revenues, or some other pool. The top performerbonus is paid to the new members for performing certain activities, suchas attending conferences, webinars, meetings, signing up personalconnection entities, adding entity groups to their networks, and soforth.

Example Transaction System

FIG. 7 is a block diagram of an example computing system usable toprovide a transaction service. The transaction service 108 may beconfigured as any suitable computing device or computing devices capableof implementing member acquisition tools. According to variousnon-limiting examples, suitable computing devices may include or be partof personal computers (PCs), servers, server farms, datacenters, specialpurpose computers, tablet computers, game consoles, smartphones, mediaplayers, combinations of these, or any other computing device(s).

Memory 702 may store program instructions that are loadable andexecutable on the processor(s) 704, as well as data generated duringexecution of, and/or usable in conjunction with, these programs.

Memory 702 includes the web service 114, the transaction platform 116,and the third party adaptors 120. The transaction platform 116 includesa service provisioning module 706 which receives service provisioninginformation for a prospective member from the web service 114. Theservice provisioning request may be for a communication service (such asa wireless phone service), a television service, an energy service, orsome other service. The service provisioning module 706 initiates theprovisioning of a new member service for the prospective member, whichincludes writing the prospective member's information to the memberdatabase 1208. The service provisioning module 706 communicates with thethird party adaptors 120 to facilitate the provisioning of the servicefor the prospective member, including the fulfillment of delivery of thehandset or other device to the prospective member.

Additionally, the service provisioning module 706 receives existingmember information that corresponds to the member that is responsiblefor signing the prospective member up to new service. For example, theprospective member may sign up for the new service after clicking on alink to the transaction service 108 in the existing member's socialnetworking page. In another example, the prospective member may sign upfor the new service by interacting with the existing member who uses amember acquisition tool on their mobile device to sign up theprospective member to new service. As part of that process, the existingmember's information is forwarded to the service provisioning module706. In the case of a soft link on the existing member's phone, and/orin the case of the prospective member clicking on a social networkinglink, the existing member information may be embedded within a resourceidentifier (such as a URL or URI). In any event, the serviceprovisioning module 706 causes the new service for the prospectivemember to be correlated in the member database 708 with the existingmember service. The prospective member may be provided with an option toverify the identity of the referring member.

A commissioning module 710 is configured to initiate commissioningcalculations for the members, such as based at least in part on arevenue sharing model according to various embodiments. This processincludes looking up members in a member's network, as indicated by thecorrelations between the members' accounts in the member database 708.In one example, if a first member signs up a second member, the firstmember receives a commission payment based at least in part on thesecond member's service payments. The commission payments may becalculated weekly, monthly, quarterly, annually, or at some other rateaccording to various embodiments. The commission payments may beone-time payments. Alternatively, the commission payments may becalculated and paid on an ongoing basis (i.e., monthly, quarterly,etc.). The commission payments may be based at least in part on aninitial sign-up of the new member, or they may be based at least in parton a portion of the new member's recurring charges. In embodiments, thecommissioning module 710 deposits the compensation as funds into anaccount held at one of the third party providers 118 via the third partyadaptors 120. The funds in the account may be tied to a debit cardissued to the entity. The commissioning module 710 may be configured totrack purchases made by the entities at participating retailers.

A relationship network module 712 determines a relationship networkassociated with an entity, such as relationship networks 400, 500, and600. The relationship network includes a plurality of network entitiesand connections between the network entities. A compensation module 714causes the entity to be provided with compensation based at least inpart on a number of entity groups within the relationship network, as isdescribed elsewhere within this Detailed Description, such as withreference to FIGS. 4-6.

In embodiments, the entity groups include network entities that havedirect connections to common network entities. In alternativeembodiments, an entity group is characterized as having a predeterminednumber of entity groups anywhere within the relationship network, notnecessarily with connections to common network entities. In embodiments,an entity group may have 2, 3, 4, 5, or more entities.

The relationship module 712 determines a subset of the plurality ofnetwork entities that have direct connections to the entity (i.e.,“personal connection entities”). The compensation module 714 maydetermine the compensation based at least in part on a first number ofentity groups within a personal network portion of the relationshipnetwork (i.e., “personal entity groups”) and on a second number ofnetwork entity groups within the relationship network (which includesthe “personal entity groups”).

As part of the compensation calculation, the compensation module 714determines a compensation tier for the entity based at least in part onthe number of entity groups in the relationship network, as is describedelsewhere within this Detailed Description, such as with reference toFIGS. 4-6. And the compensation module 714 causes the compensation to beprovided to the entity based at least in part on the compensation tier.The compensation module 714 may also calculate, and cause to beprovided, other compensation to be provided to the entity based at leastin part on the determined compensation tier and purchases made bynetwork entities within the relationship network, as is describedelsewhere within this Detailed Description.

In embodiments, achieving a compensation tier may be based least in parton constraints, such a percent rule and/or a line rule, as is describedelsewhere within this Detailed Description. To implement the line rule,the relationship network module 712 determines the number of theplurality of network entities with direct connections to the entity, andthe compensation module 714 determines the compensation tier furtherbased at least in part on whether the number of the plurality of networkentities with direct connections to the entity is greater than or equalto a minimum number for the determined compensation tier.

To implement the percent rule, the relationship network module 712determines, for individual ones of a subset of the plurality of networkentities with direct connections to the entity (i.e., the personalconnection entities), and the relationship network module 712 determinescorresponding percentages of the plurality of entity groups that connectto the entity via the individual ones of the subset. The compensationmodule 714 calculates and causes compensation to be provided based atleast in part on the corresponding percentages, as is described above.

Memory 702 also includes the motivation platform 126.

Example Operations for Providing Compensation

FIG. 8 is a flow diagram showing an example process 800 for providingcompensation based at least in part on a number of entities in arelationship network. At 802, a relationship network module, such as therelationship network module 712, determines a relationship networkassociated with an entity. The relationship network includes a pluralityof network entities and connections between the plurality of networkentities. The relationship network module may determine relationshipnetworks for a plurality of entities. In fact, all of process 800 may berepeated for each entity participating in a revenue sharing model,including those entities that are in another entity's relationshipnetwork.

At 804, a compensation module, such as the compensation module 714,counts a number of entity groups in the relationship network. This mayinclude counting entity groups within both a personal network and anextended network of the relationship network. As described elsewherewithin this Detailed Description, individual ones of the entity groupshave a predetermined number of network entities. In embodiments, theentity groups are characterized by having a predetermined number ofnetwork entities with direct connections to common network entities thatare associated with the individual ones the entity groups. Inembodiments, the relationship network is associated with one or more ofa mobile telephony service, an energy service, an entertainment service,a broadband service, or other services such as a recurring service. Theentity and/or the network entities within the relationship network aresubscribers to one or more of the mobile telephony service, an energyservice, an entertainment service, a broadband service, or otherservice.

At 806, the compensation module determines a subset of the plurality ofnetwork entities with direct connections to the entity (i.e., thepersonal connection entities). This subset may be used in part todetermine one or more of the line rule constraint and a percent ruleconstraint as described elsewhere within this Detailed Description.

At 808, the relationship network module counts the number of entitygroups within the personal network portion of the relationship network.This may be used to determine the compensation tier as is describedelsewhere within this Detailed Description.

At 810, the relationship network module determines the percentages ofthe plurality of entity groups that connect to the entity via theindividual ones of the personal connection entities. This may be used toimplement the “percent rule” constraint as is described elsewhere withinthis Detailed Description.

At 812, the compensation module determines a compensation tier that theentity has achieved based at least in part on the number of entitygroups in the relationship network and subject to the constraints (suchas the line rule constraint and the percent rule constraint or otherconstraints). In embodiments, the determined compensation tier is one ofa plurality of compensation tiers. The plurality of compensation tiersmay be characterized as being associated with corresponding minimumnumbers of entity groups, as is described elsewhere within this DetailedDescription. Subsets of the compensation tiers are grouped intocompensation bands, which may be used as a further basis to provideone-time or recurring compensation to the entity as is describedelsewhere within this Detailed Description. The number of entity groupsand the number of those entity groups with direct connections to thepersonal connection entities may determine the compensation tier.

At 814, the compensation module causes the entity to be provided withcompensation that is based at least in part on the number of entitygroups in the relationship network, such as based on the compensationtier achieved by the entity. In embodiments, the compensation isprovided based at least in part on a combination of the number of entitygroups in an extended network of the relationship network and the numberof those entity groups within a personal network portion of therelationship network.

In embodiments, the compensation may be provided based at least in parton a percent rule constraint. In other words, the compensation may bebased at least in part on the determined percentages of the number ofentity groups with connections to individual ones of the personalconnection entities. The percent rule constraint represents a maximumpercentage of the number of entity groups that can reach the entitythrough a single personal connection entity within the entity'srelationship network in order to achieve a particular compensation tieror band.

In embodiments, the compensation may be determined based at least inpart on a line rule constraint, and the compensation therefore providedbased at least in part on the number of the plurality of networkentities with direct connections to the entity (i.e., the number ofpersonal connection entities).

At 816, the compensation module causes the entity to be provided withother compensation based at least in part on purchases made by networkentities within the relationship network. The other compensation may beprovided based at least in part on a determined commissioning tier orband. For example, a determined compensation tier or band may have anassociated percentage of the set-aside revenue that is paid to theentities that reach that particular compensation tier or band.

At 818, the compensation module causes the entity to be provided with areward based at least in part on achievement of a compensation tier thatis within a compensation band not previously achieved by the entity. Inembodiments, the reward may be a one-time reward, or a periodicallyrecurring reward.

FIG. 8 depicts a flow graph that shows example processes in accordancewith various embodiments. The operations of these processes areillustrated in individual blocks and summarized with reference to thoseblocks. These processes are illustrated as a logical flow graph, eachoperation of which may represent a set of operations that can beimplemented in hardware, software, or a combination thereof. In thecontext of software, the operations represent computer-executableinstructions stored on one or more computer storage media that, whenexecuted by one or more processors, enable the one or more processors toperform the recited operations. Generally, computer-executableinstructions include routines, programs, objects, modules, components,data structures, and the like that perform particular functions orimplement particular abstract data types. The order in which theoperations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order, separated into sub-operations, and/or performed inparallel to implement the process. Processes according to variousembodiments of the present disclosure may include only some or all ofthe operations depicted in the logical flow graph.

Computer-Readable Media

Depending on the configuration and type of computing device used, memory702 may include volatile memory (such as random access memory (RAM))and/or non-volatile memory (such as read-only memory (ROM), flashmemory, etc.). Memory 702 may also include additional removable storageand/or non-removable storage including, but not limited to, flashmemory, magnetic storage, optical storage, and/or tape storage that mayprovide non-volatile storage of computer-readable instructions, datastructures, program modules, and other data for mobile device 104 ortransaction service 108.

Memory 702 is an example of computer-readable media. Computer-readablemedia includes at least two types of computer-readable media, namelycomputer storage media and communications media.

Computer storage media includes volatile and non-volatile, removable andnon-removable media implemented in any process or technology for storageof information such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, phase change memory (PRAM), static random-access memory(SRAM), dynamic random-access memory (DRAM), other types ofrandom-access memory (RAM), read-only memory (ROM), electricallyerasable programmable read-only memory (EEPROM), flash memory or othermemory technology, compact disk read-only memory (CD-ROM), digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other non-transmission medium that can be used to storeinformation for access by a computing device.

In contrast, communication media may embody computer-readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave, or other transmissionmechanism. As defined herein, computer storage media does not includecommunication media.

CONCLUSION

Although the disclosure uses language that is specific to structuralfeatures and/or methodological acts, the invention is not limited to thespecific features or acts described. Rather, the specific features andacts are disclosed as illustrative forms of implementing the invention.

1. A method, comprising: determining, by a computing system, arelationship network associated with an entity, the relationship networkincluding a plurality of network entities; counting, by the computingsystem, a number of entity groups in the relationship network,individual ones of the entity groups having a predetermined number ofnetwork entities; and causing, by the computing system, the entity to beprovided with compensation that is based at least in part on the numberof entity groups in the relationship network.
 2. The method of claim 1,wherein individual ones of the entity groups are characterized by havingnetwork entities with direct connections to common network entities thatare associated with the individual ones the entity groups.
 3. The methodof claim 1, further comprising determining a first subset of the numberof entity groups within a personal network and a second subset of thenumber of entity groups within an extended network, and wherein thecausing the entity to be provided with the compensation is based atleast in part on numbers of entity groups within the first subset andthe second subset.
 4. The method of claim 1, further comprisingdetermining, for the entity, a compensation tier that the entity hasachieved based at least in part on the number of entity groups in therelationship network, and wherein the causing the entity to be providedwith the compensation is based at least in part on the determinedcompensation tier.
 5. The method of claim 4, wherein the determinedcompensation tier is one of a plurality of compensation tiers,individual ones of the plurality of compensation tiers characterized asbeing associated with corresponding minimum numbers of entity groups. 6.The method of claim 4, wherein the determined compensation tier is oneof a plurality of compensation tiers, wherein subsets of the pluralityof compensation tiers are grouped into compensation bands, and whereinthe method further comprises causing the entity to be provided with areward based at least in part on achievement of a compensation tier thatis within a compensation band not previously achieved by the entity. 7.The method of claim 1, wherein the relationship network is associatedwith a mobile telephony service, and wherein the entity and theplurality of network entities are subscribers to the mobile telephonyservice.
 8. The method of claim 1, wherein the method further comprisescausing the entity to be provided with other compensation based at leastin part on purchases made by network entities within the relationshipnetwork.
 9. The method of claim 8, wherein the calculating of the othercompensation includes determining, for the entity, a compensation tierthat the entity has achieved based at least in part on the number ofentity groups in the relationship network, and wherein the causing theother compensation to be provided is based at least in part on apercentage associated with the determined commissioning tier.
 10. Themethod of claim 1, further comprising: determining a subset of theplurality of network entities with direct connections to the entity; anddetermining, for individual ones of the subset, correspondingpercentages of the plurality of entity groups that connect to the entityvia the individual ones of the subset; wherein the causing thecompensation to be provided is based at least in part on a highest oneof the corresponding percentages.
 11. The method of claim 1, furthercomprising determining another number of the plurality of networkentities with direct connections to the entity, and wherein the causingthe entity to be provided with the compensation is based at least inpart on the other number.
 12. A computing system, comprising: memory;one or more processors; a relationship network module stored on thememory and executable by the one or more processors to determine arelationship network associated with an entity, the relationship networkincluding a plurality of network entities; and a compensation modulestored on the memory and executable by the one more processors to causethe entity to be provided with compensation based at least in part on anumber of entity groups within the relationship network, individual onesof the entity groups having a predetermined number of network entities.13. The computing system of claim 12, wherein individual ones of theplurality of entity groups include corresponding network entities withconnections to corresponding common network entities.
 14. The computingsystem of claim 12, wherein: the relationship network module is furtherexecutable to determine a subset of the entity groups within a personalnetwork portion of the relationship network; and the compensation moduleis further executable to cause the entity to be provided with thecompensation further based at least in part on another number of thesubset of the entity groups within the personal network portion of therelationship network.
 15. The computing system of claim 12, wherein thecompensation module is further configured to: determine a compensationtier for the entity based at least in part on the number of entitygroups in the relationship network; and cause the compensation to beprovided to the entity based at least in part on the compensation tier.16. The computing system of claim 15, wherein subsets of the pluralityof compensation tiers are grouped into compensation bands, and whereinthe compensation module is further executable to cause a reward to beprovided to the entity based at least in part on achievement of acompensation tier that is within a compensation band not previouslyachieved by the entity.
 17. The computing system of claim 12, whereinthe compensation module is further configured to: determine acompensation tier for the entity based at least in part on the number ofentity groups in the relationship network; and cause other compensationto be provided to the entity based at least in part on the determinedcompensation tier and purchases made by network entities within therelationship network.
 18. The computing device of claim 17, wherein: therelationship network module is further executable to determine anothernumber of the plurality of network entities with direct connections tothe entity; and the compensation module is further executable todetermine the compensation tier further based at least in part on theother number being greater than or equal to a minimum number for thedetermined compensation tier.
 19. The computing device of claim 12,wherein: the relationship network module is further executable todetermine, for individual ones of a subset of the plurality of networkentities with direct connections to the entity, correspondingpercentages of the plurality of entity groups that connect to the entityvia the individual ones of the subset; and the compensation module isfurther executable to cause the compensation to be provided based atleast in part on the corresponding percentages.
 20. One or morecomputer-readable storage media comprising a plurality of instructionsexecutable by one or more processors of a computing device to cause thecomputing device to: determine a relationship network associated with anentity, the relationship network including a plurality of networkentities; count a number of entity groups in the relationship network,individual ones of the entity groups having a predetermined number ofnetwork entities; and cause the entity to be provided with compensationthat is based at least in part on the number of entity groups in therelationship network. 21-25. (canceled)